Is your QA team a bottleneck? Learn why the traditional "inspection" model fails and how to build a culture of quality where engineers own their work, inspired by the principles of W. Edwards Deming.

Deciding on a tech stack? Learn why the choice between .NET and open-source languages like Python isn't about cost anymore. This guide explores TCO, developer salaries, and long-term maintenance for startups.

Ready to build AI-powered apps? Discover how .NET developers can create powerful generative AI solutions using C#, ML.NET, and Semantic Kernel. Learn to leverage existing skills to build enterprise-grade chatbots, content generators, and more - Python not required.

Recently, I explored using Semantic Kernel and OpenAI for more accurate page scanning. By converting HTML to markdown and extracting metatags with XPath, I reduced input size and improved efficiency. OpenAI’s new JSON output feature further allowed me to receive structured data, making the process more reliable.

Goldratt provides 6 thinking processes as part of TOC and two of them are systematic approaches for resolving conflict. These thinking processes are Evaporating Cloud (Conflict Resolution Diagram) and Current Reality Tree (CRT). The evaporating cloud process is the simpler approach that can be used to solve most conflicts and is a frequently used tool in my toolbelt.

The Theory of Constraints (TOC) is a management philosophy and methodology developed by Eliyahu M. Goldratt. It focuses on improving organizational performance by identifying and addressing constraints, which are bottlenecks or limiting factors that impede the system's ability to achieve its goals.

Dr. Eliyahu M. Goldratt, author of The Goal and father of the Theory of Constrain identified Four questions necessary to realize the full benefits of adopting a new technology. These Four questions can be used to help your organization realize order of magnitude advantages when adopting new technologies like the Cloud.